chore: Upgrade framework to v1.17.4 (auto) - #174

Summary

• Upgrade the framework dependency to v1.17.4.
• Filesystem feature tests start their MinIO container from an image that is still published, using the credential variables MinIO reads today.

Why

This branch bumps the framework to v1.17.4. With that bump the filesystem suite could no longer start its MinIO container: minio/minio is no longer published on Docker Hub, so the image could not be pulled, and the pre-2021 MINIO_ACCESS_KEY / MINIO_SECRET_KEY variables are ignored by current MinIO releases, so the client could never authenticate even when a container did start. Both failures happen before any assertion runs.

The test now pulls a published rebuild of the last MinIO release and passes the root credentials through the names MinIO reads today, so the minio disk is exercised again in CI. Client credentials, bucket creation and the policy are untouched.

// Before: the image was gone from Docker Hub and its credentials were ignored
docker := testingdocker.NewImageDriver(contractsdocker.Image{
	Repository: "minio/minio",
	Tag:        "latest",
	Cmd:        []string{"server", "/data"},
	Env: []string{
		"MINIO_ACCESS_KEY=" + minioAccessKey,
		"MINIO_SECRET_KEY=" + minioSecretKey,
	},
	ExposedPorts: []string{"9000"},
})

// After: a published image, with the credential variables MinIO reads today
docker := testingdocker.NewImageDriver(contractsdocker.Image{
	Repository: "coollabsio/minio",
	Tag:        "RELEASE.2025-10-15T17-29-55Z",
	Cmd:        []string{"server", "/data"},
	Env: []string{
		"MINIO_ROOT_USER=" + minioAccessKey,
		"MINIO_ROOT_PASSWORD=" + minioSecretKey,
	},
	ExposedPorts: []string{"9000"},
})